Especificación de Componentes MDA para Patrones de Diseño

The Model Driven Architecture (MDA) promotes the use of models and model transformations for developing software systems. The idea behind MDA is to manage the evolution from Platform Independent Models to Platform Specific Models that can be used to generate executable components and applications. The concepts of metamodels and metamodel-based model transformations are critical in MDA. In this paper, we analyze how to specify reusable components for design patterns in a way that fit MDA very closely. To define families of reusable components we describe a “megamodel” that refers to metamodels and model transformations organized into an architectural framework. We propose an integration of formal and semiformal specifications to specify MDA mega-components. Our formalization focuses on interoperability of formal languages in Model Driven Development (MDD).La Arquitectura Model Driven (MDA) promueve el uso de modelos y transformaciones de modelos para desarrollar sistemas de software. La idea central de MDA es manejar la evolución de modelos independientes de la plataforma a modelos específicos a la plataforma que pueden ser usados para generar componentes ejecutables y aplicaciones. En el contexto MDA los metamodelos y las transformaciones basadas en metamodelos son esenciales. En este artículo describimos como especificar componentes para patrones de diseño alineados a MDA. Para definir familias de componentes reusables presentamos un “megamodelo” que integra metamodelos y refinamientos organizados en un framework arquitectural. Proponemos integrar especificaciones semiformales y formales para especificar mega-componentes MDA. Nuestra formalización se centra en la interoperabilidad de lenguajes formales en el desarrollo Model Driven (MDD)

Assessing the identity of the variety "Pedro Giménez" grown in Argentina through the use of microsatellite markers.

'Pedro Giménez' es una variedad criolla blanca cultivada en Argentina, principalmente en las provincias de Mendoza y San Juan, siendo la variedad con la mayor superficie entre las uvas blancas de vinificación. Su origen es desconocido, como también su relación con la variedad española 'Pedro Ximénez', cultivada especialmente en la región de Jerez, España. En trabajos previos se ha probado que la mayoría de las variedades criollas existentes en América se habrían originado del cruzamiento de 'Moscatel de Alejandría' x 'Criolla Chica'. El presente trabajo tuvo como objetivos comparar las variedades 'Pedro Giménez' y 'Pedro Ximénez', y establecer relaciones de parentesco con 'Moscatel de Alejandría' y 'Criolla Chica'. Se utilizaron 18 loci microsatélites nucleares y 3 loci microsatélites de cloroplasto. 'Pedro Giménez' compartió sólo el 38% de los alelos con 'Pedro Ximénez', por lo que se pudo inferir que se trata de variedades diferentes. En todos los loci polimórficos nucleares analizados 'Pedro Giménez' compartió uno de los alelos con 'Moscatel de Alejandría' y el otro con 'Criolla Chica'. Estos datos, junto con el resultado del análisis de SSR de cloroplastos, avalan la hipótesis que, como muchas de las variedades criollas, 'Pedro Giménez' sería fruto del cruzamiento entre estos dos progenitores, siendo 'Criolla Chica' probablemente el progenitor materno.´Pedro Giménez´ is a white criolla variety cropped in Argentina, mainly in Mendoza and San Juan, being the most planted white variety destined for wine making in the country. Its origin remains unknown, as well as its relationship with Spanish variety ´Pedro Ximénez´, mostly grown in Jerez, Spain. Previous works have probed that most of Criollas varieties existing in America at the moment, are the offspring of ´Muscat of Alexandria´ x ´Criolla Chica´. The aim of the present work was to compare ´Pedro Giménez´ with the Spanish variety ´Pedro Ximénez´, and to establish its degree of relatedness to ´Muscat of Alexandria´ and ´Criolla Chica´. Therefore we used a set of 18 nuclear SSR loci and 3 chloroplast SSR loci. ´Pedro Giménez´ shared only 38% of the alleles under analysis with ´Pedro Ximénez´, indicating that they are indeed two different varieties. In all 18 polymorphic nuclear SSR loci ´Pedro Giménez´ shared 50% of its alleles with ´Muscat of Alexandria´, while the other 50% of the alleles present in ´Pedro Giménez´ were also present in ´Criolla Chica´. This data, along with those from the chloroplast SSR analysis, strongly suggest that ´Pedro Giménez´ is the progeny of ´Muscat of Alexandria´ x ´Criolla Chica´, being the latest one the most likely female progenitor.Fil: Duran, Martin Francisco. Consejo Nacional de Investigaciones Científicas y Técnicas. Centro Científico Tecnológico Conicet - Mendoza. Instituto de Biología Agrícola de Mendoza. Universidad Nacional de Cuyo. Facultad de Ciencias Agrarias. Instituto de Biología Agrícola de Mendoza; ArgentinaFil: Agüero, Cecilia B.. University of California at Davis; Estados UnidosFil: Martínez, Liliana Estela. Universidad Nacional de Cuyo. Facultad de Ciencias Agrarias. Departamento de Ciencias Biológicas. Cátedra de Fisiología Vegetal; Argentin

Modernizing science&engineering software systems

As the demands for modernized legacy systems rise, so does the need for frameworks for information integration and tool interoperability. The Object Management Group (OMG) has adopted the Model Driven Architecture (MDA), which is an evolving conceptual architecture that aligns with this demand. MDA could help solve coupling problems of multidisciplinary character in science and engineering that consist of one or more applications, supported by one or more platforms. The objective of this paper is to describe rigorous techniques to control the evolution from science & engineering software legacy systems to MDA technologies. We propose a rigorous framework to reverse engineering code in the context of MDA. Considering that validation, verification and consistency are crucial activities in the modernization of systems that are critical to safety, security and economic profits, our approach emphasizes the integration of MDA with formal methods

A Quality Model for Actionable Analytics in Rapid Software Development

Background: Accessing relevant data on the product, process, and usage perspectives of software as well as integrating and analyzing such data is crucial for getting reliable and timely actionable insights aimed at continuously managing software quality in Rapid Software Development (RSD). In this context, several software analytics tools have been developed in recent years. However, there is a lack of explainable software analytics that software practitioners trust. Aims: We aimed at creating a quality model (called Q-Rapids quality model) for actionable analytics in RSD, implementing it, and evaluating its understandability and relevance. Method: We performed workshops at four companies in order to determine relevant metrics as well as product and process factors. We also elicited how these metrics and factors are used and interpreted by practitioners when making decisions in RSD. We specified the Q-Rapids quality model by comparing and integrating the results of the four workshops. Then we implemented the Q-Rapids tool to support the usage of the Q-Rapids quality model as well as the gathering, integration, and analysis of the required data. Afterwards we installed the Q-Rapids tool in the four companies and performed semi-structured interviews with eight product owners to evaluate the understandability and relevance of the Q-Rapids quality model. Results: The participants of the evaluation perceived the metrics as well as the product and process factors of the Q-Rapids quality model as understandable. Also, they considered the Q-Rapids quality model relevant for identifying product and process deficiencies (e.g., blocking code situations). Conclusions: By means of heterogeneous data sources, the Q-Rapids quality model enables detecting problems that take more time to find manually and adds transparency among the perspectives of system, process, and usage.Comment: This is an Author's Accepted Manuscript of a paper to be published by IEEE in the 44th Euromicro Conference on Software Engineering and Advanced Applications (SEAA) 2018. The final authenticated version will be available onlin

El bambú la mejor analogía para la construcción de servicio

El texto nos ilustra la importancia que toma el servicio al cliente desde una herramienta, hasta un valor agregado y de competencia servir es una habilidad del ser humano para los seres humanos esto es lo que ha venido trabajando las organizaciones apoyadas en el coaching, inteligencia emocional, la Programación Neurolingüística, para que todo el equipo de las organizaciones formen bases sólidas y logren entregas oportunas en sus productos, con excelente calidad, en forma personalizada, con calidez y de forma autentica

Recovering Sequence Diagrams from Object-oriented Code

Software modernization is a current research area in the software industry intended to transform an existing software system to a new one satisfying new demands. The initiative Architecture-Driven Modernization (ADM) helps software developers in tackling reverse engineering, software evolution and, software modernization in general. To support modernization problems, the ADM Task Force has defined a set of metamodels such as KDM (Knowledge Discovery Metamodel), being the Eclipse-MDT MoDisco project the official support for software modernization. We propose the application of ADM principles to provide relevant model-based views on legacy systems. We describe a framework to reverse engineering models from object-oriented code. In this context, we show how to recover UML sequence diagrams from Java code. We validate our approach by using ADM standards and MoDisco platform. Our research can be considered a contribution to the MoDisco community; MoDisco does not support reverse engineering of sequence diagrams and, on the other hand, the MoDisco KDM Discover was used and enriched to obtain the required information for recovering interaction diagrams

Software empresarial para flujos de trabajo SEFT

Este proyecto trata del desarrollo de un Software Empresarial para Flujos de Trabajo - SEFT y los beneficios que provee, este software permite a las empresas agilizar sus procesos documentales, disminuir el uso de papelería, obtener menores pérdidas de información, reducir los tiempos con que se realizan los tramites, lo que conlleva a un aumento en la productividad y disminución de costos.This project is about the development of SEFT a workflow Enterprise Software and the benefits it provides, this software enables companies to streamline their document processes, reduce the use of stationery, get minor losses of information, reduce the time of formalities perform, which leads to increased productivity and reduce costs

Unraveling the origin of the cultivar ‘Bonarda’ in Argentina using microsatellite molecular markers

‘Bonarda’ es una variedad de vid que en Argentina se cultiva principalmente en las provincias de Mendoza y San Juan, representa el segundo cepaje tinto en superficie nacional cultivada y es considerada con gran potencial para la elaboración de vinos tintos de alta calidad. Existe incertidumbre respecto a su origen en el país. La descripción ampelográfica de la ‘Bonarda’ cultivada en Argentina remarca gran nivel de similitud con la variedad italiana ‘Bonarda Piemontesa’ y con la variedad francesa ‘Corbeau’. En un trabajo previo, basado en el uso de marcadores moleculares, se demostró que ‘Bonarda’ se diferencia de ‘Bonarda Piamontesa’ y es idéntica a ‘Corbeau’. El objetivo de este trabajo fue confirmar la identidad de esta variedad empleando un gran número de loci microsatélites de tal manera de cubrir -en lo posible- la mayor parte del genoma. Se analizaron 17 accesiones de ‘Bonardas’ procedentes de distintos puntos geográficos de las provincias de Mendoza y San Juan, y de la variedad francesa ‘Corbeau’. Para las reacciones de PCR se usaron 13 loci microsatélites. Todas las accesiones de ‘Bonarda’ fueron idénticas entre sí e idénticas a la variedad francesa Corbeau, por lo que se concluye que se trata de la misma variedad. Se propone que la variedad ‘Bonarda’ cultivada en Mendoza y San Juan sea denominada ‘Bonarda-Argentina’, para diferenciarla de las italianas, pero a sabiendas, con un alto nivel de confianza, que corresponde a la variedad noble francesa ‘Corbeau’.'Bonarda' is the second most cultivated red variety in Argentina, mainly in the provinces of Mendoza and San Juan. In the past few years it has been valued for its great potential for the production of high quality wines. The origin of this variety was uncertain. The ampelographic description of the Argentine 'Bonarda' shows high level of similarity to the Italian variety 'Bonarda Piemontese,' and the French variety 'Corbeau'. However, recent work using molecular markers has shown that 'Bonarda' differs from ‘Bonarda Piedmontese’ and is identical to 'Corbeau'. The aim of this study was to confirm the identity of this variety using a larger number of microsatellite loci in such a way to cover, if possible, the entire genome. We analyzed 17 accessions of 'Bonarda' from the provinces of Mendoza and San Juan, Argentina, and the French variety 'Corbeau' with 13 microsatellite loci. All accessions of 'Bonarda' were identical to each other and to the French variety ‘Corbeau’, confirming that it is the same variety. It is proposed that the variety 'Bonarda' grown in Mendoza and San Juan is called 'Bonarda from Argentina' to distinguish it from the Italian Bonarda, but knowing, with a high confidence level, that corresponds to the noble French variety 'Corbeau'.Fil: De Rosas, María Inés. Universidad Nacional de Cuyo. Facultad de Ciencias Agrarias. Departamento de Ciencias BiológicasFil: Martínez, Liliana. Universidad Nacional de Cuyo. Facultad de Ciencias Agrarias. Departamento de Ciencias Biológica